src/pages/_data/navigation/mainNav.json5 (1)

60-60: Navigation entry verified; optional casing nit remains

• Confirmed src/pages/build/getting-an-agents-status.md exists with frontmatter
    • Title matches: title: "Getting an Agent's Status"
• Verified the nav item in src/pages/_data/navigation/mainNav.json5 at line 60 points to /build/getting-an-agents-status/
• All existing cross-references in src/pages/build/*.md resolve correctly to the new slug

Optional nitpick:

• Across your Build docs (e.g. src/pages/build/dht-operations.md), “DHT operations” sometimes appears as “DHT Operations.” Consider standardizing this casing for consistency.

src/pages/build/validation.md (1)

13-13: Fix unordered-list indentation (MD007) for the new bullet.

The nested list item is indented by 4 spaces but the linter expects 2. Adjust just this line (and consider normalizing the surrounding items in a follow-up).

-    * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent
+  * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent

src/pages/build/index.md (1)

75-76: Wording/casing consistency nit for the new Validation topic.

The description is fine. For consistency with other bullets and the Validation page, consider:

• Using sentence case for link text/description uniformly across the section.
• Optionally aligning the description with the same phrasing used on /build/validation/.

-* [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent
+* [Getting an agent's status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent

If the site style guide prefers title case in link text, keep the original casing and ignore this suggestion. Please confirm which convention the docs team wants to follow.

src/pages/build/genesis-self-check-callback.md (1)

5-14: Normalize nested list indentation (MD007) in the new “In this section” block.

The nested bullets are indented by 4 spaces; the linter expects 2.

 * [Validation](/build/validation/)
-    * `genesis_self_check` Callback (this page) --- writing a function to control access to a network
-    * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
-    * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- Deterministically retrieving DHT data for use in validation
-    * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
-    * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent
+  * `genesis_self_check` Callback (this page) --- writing a function to control access to a network
+  * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
+  * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- deterministically retrieving DHT data for use in validation
+  * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
+  * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent

Note: also lowercased “Deterministically” mid-sentence.

src/pages/build/dht-operations.md (4)

5-15: Align nested list indentation (MD007) in the new “In this section” block.

Same indentation issue as other pages; use 2 spaces for nested bullets.

 * [Validation](/build/validation/)
-    * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
-    * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
-    * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- Deterministically retrieving DHT data for use in validation
-    * DHT operations (this page) --- advanced details on the underlying data structure used in DHT replication and validation
-    * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent
+  * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
+  * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
+  * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- deterministically retrieving DHT data for use in validation
+  * DHT operations (this page) --- advanced details on the underlying data structure used in DHT replication and validation
+  * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent

---

84-85: Fix list indentation for the “Effect” bullet under RegisterDeleteLink (MD007).

Indent is 8 spaces; expected 4 for this level.

-        * Effect: Mark a link as deleted, without removing the actual data.
+    * Effect: Mark a link as deleted, without removing the actual data.

---

69-69: Minor typo: double “the”.

“pointing the the entry and action that replace it.”

-        * Effect: Mark an entry creation action as being replaced by a new one, pointing the the entry and action that replace it. **An entry and its creation action can have multiple actions updating them.**
+        * Effect: Mark an entry creation action as being replaced by a new one, pointing to the entry and action that replace it. **An entry and its creation action can have multiple actions updating them.**

---

86-91: WarrantOp docs link verified; minor nit on ActivityRequest::Status

Verified that the docs.rs URL for WarrantOp resolves successfully (HTTP 200), so the link and entity name are correct.

Two small suggestions to tighten the guidance:

• In the “Warrant operations” section, explicitly call out that using get_agent_activity with ActivityRequest::Status will include warrant operations, so readers know they don’t need a full activity range to retrieve them.
• (Optional) Remind readers that warrant operations are system-only—no custom validation code is required.

Relevant location:

• File: src/pages/build/dht-operations.md (around lines 86–91)

src/pages/build/must-get-host-functions.md (1)

5-14: Fix nested list indentation (MD007) in the topic-list block.

markdownlint expects a 2-space indent for nested unordered lists. Current items are indented by 4 spaces, which may affect rendering consistency.

Apply this diff:

 * [Validation](/build/validation/)
-    * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
-    * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
-    * `must_get_*` Host Functions (this page) --- Deterministically retrieving DHT data for use in validation
-    * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
-    * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent
+  * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
+  * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
+  * `must_get_*` Host Functions (this page) --- Deterministically retrieving DHT data for use in validation
+  * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
+  * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent

src/pages/build/validate-callback.md (1)

5-14: Fix nested list indentation (MD007) in the topic-list block.

Use a 2-space indent for the nested bullets to satisfy markdownlint and ensure consistent rendering.

Apply this diff:

 * [Validation](/build/validation/)
-    * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
-    * `validate` Callback (this page) --- basic callback, examples using stub functions
-    * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- Deterministically retrieving DHT data for use in validation
-    * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
-    * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent
+  * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
+  * `validate` Callback (this page) --- basic callback, examples using stub functions
+  * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- Deterministically retrieving DHT data for use in validation
+  * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
+  * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent

src/pages/resources/glossary.md (1)

933-943: Clarify retrieval and usage: how warrants surface to app code.

The definition is solid. Consider adding one sentence linking warrants to retrieval via agent activity to anchor cross-page references.

Apply this diff:

 Warrants are not produced for invalid warrants.
+
+Warrants are retrievable by peers via the agent’s activity authorities (for example, exposed to zome code in the response from `get_agent_activity`), enabling apps to factor them into agent-status checks without querying the entire source chain.

src/pages/build/getting-an-agents-status.md (3)

8-14: Fix nested list indentation (MD007) in the topic-list block.

Match other pages with a 2-space indent for nested bullets.

Apply this diff:

 * [Validation](/build/validation/)
-    * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
-    * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
-    * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- Deterministically retrieving DHT data for use in validation
-    * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
-    * Getting an Agent's Status (this page) --- checking for invalid actions committed by another agent
+  * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
+  * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
+  * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- Deterministically retrieving DHT data for use in validation
+  * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
+  * Getting an Agent's Status (this page) --- checking for invalid actions committed by another agent

---

126-133: Minor wording: “outside of the scope” → “outside the scope”.

Tighten phrasing.

Apply this diff:

-Vulnerabilities like this are outside of the scope of this document; we recommend you get a third-party security audit for any high-risk hApp involving a multi-party agreement process.
+Vulnerabilities like this are outside the scope of this document; we recommend a third-party security audit for any high-risk hApp involving a multi-party agreement process.

---

141-146: Deduplicate references and add ChainStatus reference.

Remove the duplicate ActivityRequest entry; consider adding a ChainStatus reference to match the code samples.

Apply this diff:

 * [`hdk::chain::get_agent_activity`](https://docs.rs/hdk/latest/hdk/chain/fn.get_agent_activity.html)
 * [`holochain_zome_types::query::ActivityRequest`](https://docs.rs/holochain_zome_types/latest/holochain_zome_types/query/enum.ActivityRequest.html)
 * [`holochain_zome_types::query::ChainQueryFilter`](https://docs.rs/holochain_zome_types/latest/holochain_zome_types/query/struct.ChainQueryFilter.html)
-* [`holochain_zome_types::query::ActivityRequest`](https://docs.rs/holochain_zome_types/latest/holochain_zome_types/query/enum.ActivityRequest.html)
 * [`holochain_zome_types::query::AgentActivity`](https://docs.rs/holochain_zome_types/latest/holochain_zome_types/query/struct.AgentActivity.html)
+* [`holochain_zome_types::query::ChainStatus`](https://docs.rs/holochain_zome_types/latest/holochain_zome_types/query/enum.ChainStatus.html)

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

src/pages/build/must-get-host-functions.md (1)

5-14: Nice addition — cross-page navigation improves discoverability.

The “In this section” block aligns with other Validation pages and helps readers follow the flow.

src/pages/build/validate-callback.md (1)

16-18: Intro copy reads well and correctly frames validate’s scope.

Clear and accurate description of Op, action/entry context, and dependency handling via must_get_*.

src/pages/build/getting-an-agents-status.md (3)

94-104: Confirm chain filter API: sequence_range + ActionHashTerminated.

Method and enum names in ChainQueryFilter/range types have changed in past releases. Ensure sequence_range(ChainQueryFilterRange::ActionHashTerminated(proposal_hash, 0)) compiles for your target HDK; otherwise, substitute the current equivalent.

If needed, please paste your HDK version; I can propose an exact, compiling filter snippet.

---

20-31: Scope and positioning: correct to keep this out of validation callbacks.

Good call highlighting non-determinism; this aligns with Acceptance Criteria to focus on agent-status concerns (warrants, forks) rather than general chain queries.

---

91-95: Typo in return type & HDK API validation needed

• In src/pages/build/getting-an-agents-status.md (lines 91–95), update the return type:

  - pub fn is_proposal_currently_good(initiator: AgentPubKey, proposal_hash: ActionHash) -> ExternResult<PropsalStatus> {
  + pub fn is_proposal_currently_good(initiator: AgentPubKey, proposal_hash: ActionHash) -> ExternResult<ProposalStatus> {

• Manually confirm that ProposalStatus (not PropsalStatus) is the correct enum in your HDK/holochain_zome_types version.
• Verify that the helper functions and types—get_agent_activity, ChainQueryFilter::new(), and any chained filter-builder methods—exist and haven’t changed in your targeted HDK release.

src/pages/build/getting-an-agents-status.md (2)

28-29: Broken glossary anchor: use “Validation authority”.

Replace non-existent “dht-authority” anchor with the defined glossary anchor; also pluralize “authority” per glossary entry.

-A warrant is created for _any_ DHT operation that fails app validation, and sent to the [authority](/resources/glossary/#dht-authority) responsible for the warranted author's [agent ID](/build/identifiers/#agent) address. No warrants are created for chain forks, because a warrant is simply a way of informing other agents of an incident on data they might not be an authority on, and agent ID authorities already watch for chain forks.<!-- TODO: change this language if chain fork warrants become a thing -->
+A warrant is created for _any_ DHT operation that fails app validation, and sent to the [validation authorities](/resources/glossary/#validation-authority) responsible for the warranted author's [agent ID](/build/identifiers/#agent) address. No warrants are created for chain forks, because a warrant is simply a way of informing other agents of an incident on data they might not be an authority on, and agent ID authorities already watch for chain forks.<!-- TODO: change this language if chain fork warrants become a thing -->

---

59-61: Broken glossary anchor in note: “heighbor” → “neighbor”.

-However, most authorities with good connectivity to their [neighbors](/resources/glossary/#heighbor) will discover invalid data and chain forks and publish warrants within seconds after the data is published.
+However, most authorities with good connectivity to their [neighbors](/resources/glossary/#neighbor) will discover invalid data and chain forks and publish warrants within seconds after the data is published.

src/pages/build/getting-an-agents-status.md (6)

24-25: Minor wording: “provides” reads stronger than “gives”.

-You can do this with the [`get_agent_activity`](https://docs.rs/hdk/latest/hdk/chain/fn.get_agent_activity.html) host function, which gives information about both chain forks and collected **warrants** for an agent.
+You can do this with the [`get_agent_activity`](https://docs.rs/hdk/latest/hdk/chain/fn.get_agent_activity.html) host function, which provides information about both chain forks and collected **warrants** for an agent.

---

8-14: Fix nested list indentation (markdownlint MD007).

Adjust indentation of the “In this section” nested bullets from 4 to 2 spaces.

 * [Validation](/build/validation/)
-    * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
-    * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
-    * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- Deterministically retrieving DHT data for use in validation
-    * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
-    * Getting an Agent's Status (this page) --- checking for invalid actions committed by another agent
+  * [`genesis_self_check` Callback](/build/genesis-self-check-callback/) --- writing a function to control access to a network
+  * [`validate` Callback](/build/validate-callback/) --- basic callback, examples using stub functions
+  * [`must_get_*` Host Functions](/build/must-get-host-functions/) --- Deterministically retrieving DHT data for use in validation
+  * [DHT operations](/build/dht-operations/) --- advanced details on the underlying data structure used in DHT replication and validation
+  * Getting an Agent's Status (this page) --- checking for invalid actions committed by another agent

---

49-56: Rust: simplify status+warrants check with matches! and is_empty().

Your tuple pattern works, but this is a bit clearer and avoids magic number 0.

-    // The agent is safe if their chain has no forks or invalid data,
-    // and no other authorities have produced warrants.
-    if let (ChainStatus::Valid(_), 0) = (agent_state.status, agent_state.warrants.len()) {
-        return Ok(true);
-    }
-
-    Ok(false)
+    // The agent is safe if their chain has no forks or invalid data,
+    // and no other authorities have produced warrants.
+    Ok(
+        matches!(agent_state.status, ChainStatus::Valid(_))
+            && agent_state.warrants.is_empty(),
+    )

---

116-121: Rust: use is_empty() for idiomatic checks.

Small readability wins; also keeps style consistent with the earlier sample.

-            if initiator_state.warrants.len() > 0 {
+            if !initiator_state.warrants.is_empty() {
                 return Ok(ProposalStatus::Invalid);
             }
-            if initiator_state.valid_activity.len() == 0 {
+            if initiator_state.valid_activity.is_empty() {
                 return Ok(ProposalStatus::NotAvailable);
             }

---

134-134: Tighten phrasing: “outside the scope”.

-Vulnerabilities like this are outside of the scope of this document; we recommend you get a third-party security audit for any high-risk hApp involving a multi-party agreement process.
+Vulnerabilities like this are outside the scope of this document; we recommend you get a third-party security audit for any high-risk hApp involving a multi-party agreement process.

---

141-147: References: remove duplicate ActivityRequest entry (line 146).

Avoid duplication; the first ActivityRequest bullet already covers it.

 * [`holochain_zome_types::query::ChainQueryFilter`](https://docs.rs/holochain_zome_types/latest/holochain_zome_types/query/struct.ChainQueryFilter.html)
-* [`holochain_zome_types::query::ActivityRequest`](https://docs.rs/holochain_zome_types/latest/holochain_zome_types/query/enum.ActivityRequest.html)
 * [`holochain_zome_types::query::AgentActivity`](https://docs.rs/holochain_zome_types/latest/holochain_zome_types/query/struct.AgentActivity.html)

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

src/pages/build/dht-operations.md (1)

81-85: Anchor fixed for RegisterDeleteLink — looks good.

The link text and anchor now both reference RegisterDeleteLink. This resolves the prior issue.

src/pages/build/getting-an-agents-status.md (1)

24-29: Glossary/anchor corrections look good.

The glossary reference now uses validation-authority and the warrants intro aligns with the new DHT operations section.

src/pages/build/dht-operations.md (1)

86-91: Warrant operations section is clear; consider tightening cross-references.

Optional polish:

• Mention explicitly that get_agent_activity returns warrants with either ActivityRequest::Status or ActivityRequest::Full, to reinforce the retrieval path from here.
• Optionally link “basis address” here to the glossary entry for quick recall, since you introduce a new op type.

Suggested minimal tweak:

-There's one final DHT operation type, a [`WarrantOp`](https://docs.rs/holochain_types/latest/holochain_types/warrant/struct.WarrantOp.html). Rather than being produced from an action, it gets produced by a validator when they discover an invalid operation. Its basis address is the public key of the author of the operation, which means warrants get collected on the agent ID address and can be [retrieved with `get_agent_activity`](/build/getting-an-agents-status/).
+There's one final DHT operation type, a [`WarrantOp`](https://docs.rs/holochain_types/latest/holochain_types/warrant/struct.WarrantOp.html). Rather than being produced from an action, it gets produced by a validator when they discover an invalid operation. Its basis address is the public key of the author of the operation (the agent's [basis address](/resources/glossary/#basis-address)), which means warrants get collected on the agent ID address and can be retrieved via [`get_agent_activity`](/build/getting-an-agents-status/) using either `ActivityRequest::Status` or `ActivityRequest::Full`.

src/pages/build/getting-an-agents-status.md (3)

49-55: Prefer matches! and is_empty() for clarity (and to avoid moving status).

Your tuple-pattern works, but matches! reads clearer and avoids moving agent_state.status.

Apply this diff:

-    // The agent is safe if their chain has no forks or invalid data,
-    // and no other authorities have produced warrants.
-    if let (ChainStatus::Valid(_), 0) = (agent_state.status, agent_state.warrants.len()) {
-        return Ok(true);
-    }
-
-    Ok(false)
+    // The agent is safe if their chain has no forks or invalid data,
+    // and no other authorities have produced warrants.
+    Ok(
+        matches!(agent_state.status, ChainStatus::Valid(_))
+            && agent_state.warrants.is_empty()
+    )

---

59-61: Avoid time guarantees; soften wording to “typically quickly.”

“Within seconds” may overpromise depending on network conditions. Consider hedging to avoid misleading readers.

-However, most authorities with good connectivity to their [neighbors](/resources/glossary/#neighbor) will discover invalid data and chain forks and publish warrants within seconds after the data is published.
+However, most authorities with good connectivity to their [neighbors](/resources/glossary/#neighbor) typically discover invalid data and chain forks and publish warrants quickly after the data is published.

---

108-124: Minor idioms: use is_empty() for collections.

No logic issues spotted. Using is_empty() communicates intent and is idiomatic.

-            if initiator_state.warrants.len() > 0 {
+            if !initiator_state.warrants.is_empty() {
                 return Ok(ProposalStatus::Invalid);
             }
-            if initiator_state.valid_activity.len() == 0 {
+            if initiator_state.valid_activity.is_empty() {
                 return Ok(ProposalStatus::NotAvailable);
             }

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

src/pages/build/dht-operations.md (1)

5-14: 4‑space list indentation is fine; ensure the linter is configured to allow it.

MD007 warnings are expected here because the list uses 4 spaces. Given the repo preference (4 spaces), confirm .markdownlint.json includes MD007 with "indent": 4, or that the CI linter is otherwise configured to accept this style.

If you want, I can add the config via a follow-up PR.

src/pages/build/getting-an-agents-status.md (3)

5-14: 4‑space list indentation acknowledged; align linter config to avoid MD007 noise.

Same note as in dht-operations: if CI runs markdownlint with MD007’s default (2), it will complain. Configure MD007 to "indent": 4 in .markdownlint.json to reflect repo convention.

---

41-47: Confirm current HDK signature/variants in your target Holochain version.

The call pattern get_agent_activity(agent, ChainQueryFilter::new(), ActivityRequest::Status) looks correct. Just a heads-up to verify against the HDK version this doc targets so the snippet doesn’t drift if parameters or enum names change.

---

96-106: Filter by action hash: confirm ChainQueryFilterRange::ActionHashTerminated semantics.

The intent is clear (ensure the proposal action exists). Double-check the range constructor and the “0” termination offset for the targeted HDK to ensure it selects exactly the action (not a window that could miss or over-include).

If needed, I can propose an alternative using ChainQueryFilter::action_sequence_range or an explicit action hash set once we confirm the current API.

src/pages/resources/glossary.md (1)

933-942: Consider addressing the long line lengths flagged by markdownlint.

While the content updates to the warrant definition are accurate and well-structured, several lines exceed the 80-character limit. Consider breaking longer sentences into multiple lines for better readability and consistency with the project's markdown linting rules.

For example, line 938 could be reformatted:

-The [basis address](#basis-address) of a warrant is the [agent ID](#agent-id) of the author of the invalid operation; hence, it is sent to and collected by the [validation authorities](#validation-authority) responsible for the agent ID basis address.
+The [basis address](#basis-address) of a warrant is the [agent ID](#agent-id) of 
+the author of the invalid operation; hence, it is sent to and collected by the 
+[validation authorities](#validation-authority) responsible for the agent ID basis address.

src/pages/build/getting-an-agents-status.md (1)

152-152: Add missing trailing newline.

The file should end with a single newline character to comply with markdown linting rules.

+

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

netlify.toml (1)

2-15: LGTM! Netlify link checking plugin properly configured.

The plugin configuration is well-structured with appropriate settings for HTML link validation. The Google Fonts URL exclusion in skipPatterns is a common and necessary workaround for fonts.googleapis.com reliability issues during automated checks.

src/pages/resources/glossary.md (1)

935-936: Warrant definition updates align with the new documentation.

The simplified warrant conditions and explicit reference to DHT operations are consistent with the new "Getting an Agent's Status" page and the warrant operations section added to DHT operations documentation.

src/pages/build/getting-an-agents-status.md (7)

1-18: LGTM! Well-structured page introduction and navigation.

The page header, navigation section, and introduction clearly establish the purpose and context. The glossary link to warrants is correctly formatted.

---

20-31: Excellent explanation of warrant mechanics and timing considerations.

The distinction between warrants for validation failures versus chain forks is clearly explained, and the important note about non-deterministic agent state preventing use in validation callbacks is crucial for developers to understand.

---

36-56: Rust code example is correct and well-documented.

The is_agent_safe_to_interact_with function demonstrates proper usage of get_agent_activity with ActivityRequest::Status. The boolean logic using matches! macro and is_empty() check is appropriate and clearly reflects the safety criteria.

---

58-60: Important caveat about eventual consistency well-explained.

The info box appropriately warns users about the eventual consistency nature of warrants and chain forks while providing realistic expectations about discovery timing.

---

68-125: Comprehensive proposal validation example with good security considerations.

The is_proposal_currently_good function provides a thorough example of checking for a specific published action. The ProposalStatus enum covers all relevant states, and the logic properly handles different chain statuses and warrant checks.

---

127-134: Critical security warnings for time-based attacks.

The documentation appropriately highlights sophisticated attack vectors and recommends professional security audits for high-risk applications. This is essential guidance for developers working with multi-party agreements.

---

140-152: Comprehensive reference links and further reading.

The reference section provides all relevant API documentation links, and the further reading section creates good cross-connections to related concepts and build guide sections.

src/pages/build/dht-operations.md (1)

86-91: Consider breaking the long sentence for better readability.

The warrant operations description is comprehensive but the single sentence on Line 88 is quite long (467 characters). Consider splitting it into two sentences for better readability.

-There's one final DHT operation type, a [`WarrantOp`](https://docs.rs/holochain_types/latest/holochain_types/warrant/struct.WarrantOp.html). Rather than being produced from an action, it gets produced by a validator when they discover an invalid operation. Its basis address is the public key of the author of the operation, which means warrants get collected on the agent ID address and can be [retrieved with `get_agent_activity`](/build/getting-an-agents-status/).
+There's one final DHT operation type, a [`WarrantOp`](https://docs.rs/holochain_types/latest/holochain_types/warrant/struct.WarrantOp.html). Rather than being produced from an action, it gets produced by a validator when they discover an invalid operation.
+
+Its basis address is the public key of the author of the operation, which means warrants get collected on the agent ID address and can be [retrieved with `get_agent_activity`](/build/getting-an-agents-status/).

src/pages/build/validation.md (1)

13-13: Line length exceeds MD013; either wrap or codify an exception.

If you want to keep single-line bullets in topic-list blocks, prefer handling in markdownlint config (disable MD013 for these blocks). Otherwise, wrap the description to a continuation line.

Optional wrap:

-    * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent
+    * [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid
+      actions committed by another agent

src/pages/build/index.md (1)

75-75: Keep topic-list bullets under MD013 or handle via repo config.

Same note as elsewhere: either wrap the description or disable/enforce exceptions for MD013 in topic-list sections via .markdownlint config.

-* [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid actions committed by another agent
+* [Getting an Agent's Status](/build/getting-an-agents-status/) --- checking for invalid
+  actions committed by another agent

src/pages/build/must-get-host-functions.md (2)

6-6: Fix MD022 (headings need blank lines).

Add a blank line before and after the “In this section” heading inside the topic-list block.

 ::: topic-list
-### In this section {data-no-toc}
+
+### In this section {data-no-toc}
+

---

9-13: MD013 long lines in topic-list.

Wrap lines or cover via markdownlint config as a project-wide rule for topic-list sections.

src/pages/build/genesis-self-check-callback.md (2)

6-6: Fix MD022 (headings need blank lines).

 ::: topic-list
-### In this section {data-no-toc}
+
+### In this section {data-no-toc}
+

---

61-63: Narrow the Base64 import.

Avoid glob; import only what’s needed.

-use base64::*;
+use base64::engine::general_purpose::STANDARD as BASE64_STANDARD;
+use base64::Engine;

And update calls accordingly (e.g., BASE64_STANDARD.decode(s)).

src/pages/build/validate-callback.md (2)

6-6: Fix MD022 (headings need blank lines).

 ::: topic-list
-### In this section {data-no-toc}
+
+### In this section {data-no-toc}
+

---

9-13: MD013 long lines in topic-list.

Wrap or configure markdownlint exceptions for these navigation bullets.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

src/pages/build/dht-operations.md (1)

86-91: Split the WarrantOp paragraph for readability and to avoid causal implication.

Break into shorter sentences per prior suggestion; keeps the same meaning while reading cleaner.

-There's one final DHT operation type, a [`WarrantOp`](https://docs.rs/holochain_types/latest/holochain_types/warrant/struct.WarrantOp.html). Rather than being produced from an action, it gets produced by a validator when they discover an invalid operation. Its basis address is the public key of the author of the operation, which means warrants get collected on the agent ID address. Warrants can be [retrieved with `get_agent_activity`](/build/getting-an-agents-status/).
+There's one final DHT operation type, a [`WarrantOp`](https://docs.rs/holochain_types/latest/holochain_types/warrant/struct.WarrantOp.html).
+It's produced by validators when they discover an invalid operation. Its basis address is the public key of the operation's author, so warrants are collected on the agent ID address. Warrants can be [retrieved with `get_agent_activity`](/build/getting-an-agents-status/).

src/pages/build/dht-operations.md (3)

5-14: Add a blank line before the heading inside the topic-list block to satisfy MD022.

This removes the “Headings should be surrounded by blank lines” warning on Line 6.

 ::: topic-list
+
 ### In this section {data-no-toc}

---

69-69: Tiny grammar tweak for clarity.

“replace it” refers to two nouns (“entry and action”); switch to “replace them.”

-        * Effect: Mark an entry creation action as being replaced by a new one, pointing to the entry and action that replace it. **An entry and its creation action can have multiple actions updating them.**
+        * Effect: Mark an entry creation action as being replaced by a new one, pointing to the entry and action that replace them. **An entry and its creation action can have multiple actions updating them.**

---

9-13: Optional: address MD013 long-line warnings or disable the rule for docs pages.

Either wrap these long list items with proper continuation indentation, or disable MD013 in your markdownlint config for this repo/content type. Given the number of links, disabling MD013 here is reasonable.

Would you like a PR snippet for .markdownlint.json to disable MD013 (or limit it just under src/pages/)?

Also applies to: 82-82, 84-84

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

src/pages/build/getting-an-agents-status.md (1)

24-24: Fix broken glossary anchor: use “validation-authority”.

The glossary doesn’t define “dht-authority”. Link to the existing “Validation authority” entry.

-In a network where all agents are [authorities](/resources/glossary/#dht-authority) for the full DHT, all invalid data will eventually be discovered by everyone, and their Holochain conductors will automatically block the bad actor at the network level. In a sharded network, discovery of bad actors happens instead through the publishing and discovery of [**warrants**](/resources/glossary/#warrant).
+In a network where all agents are [validation authorities](/resources/glossary/#validation-authority) for the full DHT, all invalid data will eventually be discovered by everyone, and their Holochain conductors will automatically block the bad actor at the network level. In a sharded network, discovery of bad actors happens instead through the publishing and discovery of [**warrants**](/resources/glossary/#warrant).

src/pages/resources/glossary.md (2)

942-942: Clarify sentence: “invalid warrants.”

Small wording tweak improves precision.

-Warrants are not produced for invalid warrants.
+Warrants are not produced in response to invalid warrants.

---

933-942: Long lines trigger MD013; consider soft-wrapping or disabling per repo policy.

If MD013 is enforced, wrap lines to <=80 chars or add a local markdownlint override consistent with your lint config.

src/pages/build/getting-an-agents-status.md (3)

91-104: Derives for extern return type: add Deserialize + Clone.

Improves FFI ergonomics and parity with other types; harmless even if not strictly required.

-#[derive(Serialize, Debug)]
+#[derive(Serialize, Deserialize, Clone, Debug)]
 pub enum ProposalStatus {

---

106-110: Derives for extern input type: add Serialize + Clone.

Keeps symmetry with return type and common HDK patterns.

-#[derive(Deserialize, Debug)]
+#[derive(Serialize, Deserialize, Clone, Debug)]
 pub struct IsProposalCurrentlyGoodInput {

---

174-179: Add trailing newline (MD047).

Ends file with a single newline to satisfy markdownlint.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Learnt from: pdaoust
PR: holochain/docs-pages#597
File: src/pages/build/getting-an-agents-status.md:141-141
Timestamp: 2025-09-08T21:51:44.027Z
Learning: In the holochain_zome_types::query::AgentActivity struct, the correct field name is `valid_activity`, not `valid_actions`. This field contains the valid activities for an agent according to the official Rust documentation.

src/pages/build/getting-an-agents-status.md (2)

24-26: Broken glossary anchor: use “validation-authority”.

The glossary anchor is #validation-authority, not #dht-authority.

-In a network where all agents are [authorities](/resources/glossary/#dht-authority) for the full DHT,
+In a network where all agents are [authorities](/resources/glossary/#validation-authority) for the full DHT,

---

24-36: Avoid contradicting “Blocking isn’t operational yet.”

This paragraph says conductors “will automatically block,” but the callout below says blocking isn’t implemented. Rephrase to remove the claim of current automatic blocking.

-In a network where all agents are [authorities](/resources/glossary/#validation-authority) for the full DHT, all invalid data will eventually be discovered by everyone, and their Holochain conductors will automatically block the bad actor at the network level. In a [sharded](/resources/glossary/#sharding) network, however, news of bad actors spreads instead through the publishing and discovery of [**warrants**](/resources/glossary/#warrant).
+In a network where all agents are [authorities](/resources/glossary/#validation-authority) for the full DHT, all invalid data will eventually be discovered by everyone. In a [sharded](/resources/glossary/#sharding) network, news of bad actors spreads through the publishing and discovery of [**warrants**](/resources/glossary/#warrant).

src/pages/build/must-get-host-functions.md (1)

5-14: Fix MD022: add a blank line before the heading inside topic-list.

markdownlint requires a blank line before “### In this section” when nested. Insert an empty line after the opening ::: topic-list.

 ::: topic-list
+ 
 ### In this section {data-no-toc}
 
 * [Validation](/build/validation/)

src/pages/resources/glossary.md (1)

940-941: Clarify current behavior vs future blocking (keep “future‑correct” stance).

To avoid confusion with pages that state “Blocking isn’t operational yet,” add a brief note that automatic blocking is planned.

-A warrant may be used by any peer as legitimate grounds for blocking communication with the [agent](#agent) being warranted.<!-- TODO: update this if warrants ever become used as grounds for scrubbing invalid data -->
+A warrant may be used by any peer as legitimate grounds for blocking communication with the [agent](#agent) being warranted; automatic blocking by conductors is planned but not yet implemented.<!-- TODO: update this if warrants ever become used as grounds for scrubbing invalid data -->

src/pages/build/dht-operations.md (1)

5-14: Fix MD022: add a blank line before the heading inside topic-list.

Insert an empty line after ::: topic-list so the heading is surrounded by blanks.

 ::: topic-list
+ 
 ### In this section {data-no-toc}

src/pages/build/getting-an-agents-status.md (1)

5-14: Fix MD022: add a blank line before the heading inside topic-list.

Add an empty line after ::: topic-list so the heading is surrounded by blank lines.

 ::: topic-list
+ 
 ### In this section {data-no-toc}

src/pages/build/genesis-self-check-callback.md (1)

5-14: Fix MD022: add a blank line before the heading inside topic-list.

Insert an empty line after ::: topic-list so the heading is surrounded by blanks.

 ::: topic-list
+ 
 ### In this section {data-no-toc}

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Learnt from: pdaoust
PR: holochain/docs-pages#597
File: src/pages/build/getting-an-agents-status.md:141-141
Timestamp: 2025-09-08T21:51:44.027Z
Learning: In the holochain_zome_types::query::AgentActivity struct, the correct field name is `valid_activity`, not `valid_actions`. This field contains the valid activities for an agent according to the official Rust documentation.

Learnt from: pdaoust
PR: holochain/docs-pages#597
File: src/pages/resources/glossary.md:933-939
Timestamp: 2025-09-11T13:19:23.020Z
Learning: In the holochain/docs-pages repository, pdaoust prefers glossary definitions to be "future-correct" rather than strictly reflecting current implementation status, to reduce maintenance burden when features are implemented.